build(deps): bump github.com/go-telegram/bot from 1.23.0 to 1.24.0 in the go-dependencies group - #54

Sourced from github.com/go-telegram/bot's releases.

v1.24.0

• Support Bot API 10.3 (August 24, 2026 update):
  • Rich Messages: new RichMessageButton; RichTextButton (via the RichText union); RichBlockButtons, RichBlockExpandableBlockQuotation, RichBlockDocument and their InputRichBlock* counterparts (via the RichBlock / InputRichBlock unions); is_compact on RichBlockTable and InputRichBlockTable; tg://document?id= links for InputRichMessageMedia.
  • Ephemeral Messages: new EphemeralMessageParameters (with replace_callback_query_message), sent as ephemeral_message_parameters by the 13 send methods and sendRichMessage; rich_message on editEphemeralMessageText (and text made optional); show_caption_above_media on editEphemeralMessageCaption; upload of new files in editEphemeralMessageMedia; can_send_welcome_messages on ChatAdministratorRights, ChatMemberAdministrator and promoteChatMember.
  • Reply markup: new DisabledButton with the disabled field on InlineKeyboardButton; force_reply on InlineKeyboardMarkup and ReplyKeyboardMarkup.
  • General: can_stop and keep_on_stop on sendMessageDraft and sendRichMessageDraft; new MessageGenerationStopped with the stopped_message_generation field on Update (and the matching allowed-update constant); new CommunityChatJoined with community_chat_joined on Message; text, entities and is_private on UniqueGiftInfo.
• Fix: attach:// with a nil reader returns an error instead of panicking. addFormFieldInputMediaItem and addFormFieldInputStickerSlice copied the reader without checking it, and since the form is built in a goroutine with no recover, a missing MediaAttachment or StickerAttachment took the process down instead of failing the call (#296).
• Fix: can_post_stories, can_edit_stories and can_delete_stories are no longer marked omitempty on ChatAdministratorRights and ChatMemberAdministrator. They are required fields in the Bot API, so they are now always sent, matching the rest of the required rights in those types. The parameters of the same name on promoteChatMember are optional and are unchanged.
• Fix: the getUpdates loop honours retry_after on a 429 instead of its own backoff, which starts at 100ms, doubles and caps at 5s. When Telegram asked for a longer wait, the bot retried early and earned further 429s (#289).
• [BREAKING] Fix: Message.ReplyToStore was tagged reply_to_store, a typo of the Bot API field reply_to_story, so it was never unmarshalled. The field is renamed to ReplyToStory (#287).
• [BREAKING] Fix: BusinessBotRights.CanDeleteOutgoingMessages was tagged can_delete_outgoing_messages, which does not exist in the Bot API. The right was dropped on unmarshal and emitted under a key Telegram ignores. The field is renamed to CanDeleteSentMessages with the correct can_delete_sent_messages tag (#286).
• [BREAKING] ReceiverUserID and CallbackQueryID are removed from the send method params (SendMessageParams, SendPhotoParams, ...); Bot API 10.3 replaced them with EphemeralMessageParameters.

Sourced from github.com/go-telegram/bot's changelog.

v1.24.0 (2026-08-26)

• Support Bot API 10.3 (August 24, 2026 update):
  • Rich Messages: new RichMessageButton; RichTextButton (via the RichText union); RichBlockButtons, RichBlockExpandableBlockQuotation, RichBlockDocument and their InputRichBlock* counterparts (via the RichBlock / InputRichBlock unions); is_compact on RichBlockTable and InputRichBlockTable; tg://document?id= links for InputRichMessageMedia.
  • Ephemeral Messages: new EphemeralMessageParameters (with replace_callback_query_message), sent as ephemeral_message_parameters by the 13 send methods and sendRichMessage; rich_message on editEphemeralMessageText (and text made optional); show_caption_above_media on editEphemeralMessageCaption; upload of new files in editEphemeralMessageMedia; can_send_welcome_messages on ChatAdministratorRights, ChatMemberAdministrator and promoteChatMember.
  • Reply markup: new DisabledButton with the disabled field on InlineKeyboardButton; force_reply on InlineKeyboardMarkup and ReplyKeyboardMarkup.
  • General: can_stop and keep_on_stop on sendMessageDraft and sendRichMessageDraft; new MessageGenerationStopped with the stopped_message_generation field on Update (and the matching allowed-update constant); new CommunityChatJoined with community_chat_joined on Message; text, entities and is_private on UniqueGiftInfo.
• Fix: attach:// with a nil reader returns an error instead of panicking. addFormFieldInputMediaItem and addFormFieldInputStickerSlice copied the reader without checking it, and since the form is built in a goroutine with no recover, a missing MediaAttachment or StickerAttachment took the process down instead of failing the call (#296).
• Fix: can_post_stories, can_edit_stories and can_delete_stories are no longer marked omitempty on ChatAdministratorRights and ChatMemberAdministrator. They are required fields in the Bot API, so they are now always sent, matching the rest of the required rights in those types. The parameters of the same name on promoteChatMember are optional and are unchanged.
• Fix: the getUpdates loop honours retry_after on a 429 instead of its own backoff, which starts at 100ms, doubles and caps at 5s. When Telegram asked for a longer wait, the bot retried early and earned further 429s (#289).
• [BREAKING] Fix: Message.ReplyToStore was tagged reply_to_store, a typo of the Bot API field reply_to_story, so it was never unmarshalled. The field is renamed to ReplyToStory (#287).
• [BREAKING] Fix: BusinessBotRights.CanDeleteOutgoingMessages was tagged can_delete_outgoing_messages, which does not exist in the Bot API. The right was dropped on unmarshal and emitted under a key Telegram ignores. The field is renamed to CanDeleteSentMessages with the correct can_delete_sent_messages tag (#286).
• [BREAKING] ReceiverUserID and CallbackQueryID are removed from the send method params (SendMessageParams, SendPhotoParams, ...); Bot API 10.3 replaced them with EphemeralMessageParameters.

• 5842ef8 changelog: 429 retry_after, reply_to_story and delete-sent-messages fixes
• 7a43a65 fix(models): correct BusinessBotRights delete-sent-messages field (#286)
• 1400659 fix: correct reply_to_story field name and json tag on Message (#287)
• 2836b7b fix: honour retry_after on 429 in the getUpdates loop (#289)
• cacace1 fix: always send the required story rights in admin types
• 49a5abd changelog: date v1.24.0, add the attach:// nil reader fix
• 571c7a6 feat: support Bot API 10.3 (#295)
• d8a23e5 fix: return error for attach:// with a nil reader (#297)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions